翻訳と辞書
Words near each other
・ Agile (producer)
・ AGILE (satellite)
・ Agile antechinus
・ Agile application
・ Agile Automation
・ Agile Business Intelligence
・ Agile Communication Environment
・ Agile construction
・ Agile contracts
・ Agile Frameworks
・ Agile frog
・ Agile gibbon
・ Agile gracile opossum
・ Agile kangaroo rat
・ Agile leadership
Agile management
・ Agile mangabey
・ Agile manufacturing
・ Agile modeling
・ Agile Networks
・ Agile Policing Strategy
・ Agile Project Management (book)
・ Agile Property
・ Agile Risk Management
・ Agile snouted tree frog
・ Agile Software Corporation
・ Agile software development
・ Agile testing
・ Agile tit-tyrant
・ Agile Unified Process


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Agile management : ウィキペディア英語版
Agile management

Agile management, or agile process management, or simply agile refer to an iterative, incremental method of managing the design and build activities for engineering, information technology, and other business areas that aims to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development.〔''Managing Agile: Strategy, Implementation, Organisation and People'', Moran A., Springer Verlag, 2015. ISBN 978-3-319-16262-1〕 It requires capable individuals from the relevant business, openness to consistent customer input, and management openness to non-hierarchical forms of leadership. Agile can in fact be viewed as a broadening and generalization of the principles of the earlier successful array of Scrum concepts and techniques to more diverse business activities. Agile also traces its evolution to a "consensus event", the publication of the "Agile manifesto", and it has conceptual links to lean techniques, kanban , and the Six Sigma area of business ideas.
Agile X techniques may also be called extreme process management. It is a variant of iterative life cycle〔ExecutiveBrief, (Which Life Cycle Is Best For Your Project? ), PM Hut. Accessed 23. Oct 2009.〕 where deliverables are submitted in stages. The main difference between agile and iterative development is that agile methods complete small portions of the deliverables in each delivery cycle (iteration)〔(【引用サイトリンク】 title=Agile Project Management )〕 while iterative methods evolve the entire set of deliverables over time, completing them near the end of the project. Both iterative and agile methods were developed as a reaction to various obstacles that developed in more sequential forms of project organization. For example, as technology projects grow in complexity, end users tend to have difficulty defining the long term requirements without being able to view progressive prototypes. Projects that develop in iterations can constantly gather feedback to help refine those requirements. According to Jean-Loup Richet (Research Fellow at ESSEC Institute for Strategic Innovation & Services) "this approach can be leveraged effectively for non-software products and for project management in general, especially in areas of innovation and uncertainty. The end result is a product or project that best meets current customer needs and is delivered with minimal costs, waste, and time, enabling companies to achieve bottom line gains earlier than via traditional approaches.〔Richet, Jean-Loup (2013). ''Agile Innovation''. Cases and Applied Research, n°31. ESSEC-ISIS. ISBN 978-2-36456-091-8〕 Agile management also offers a simple framework promoting communication and reflection on past work amongst team members.〔(【引用サイトリンク】 title=What is Agile Management? )
Agile methods are mentioned in the ''Guide to the Project Management Body of Knowledge'' (''PMBOK Guide'') under the Project Lifecycle definition:
==See also==

*The Fifth Discipline
*Systems development life cycle
*Software development process

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Agile management」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.